System and method for migrating an agent server to an agent client device

ABSTRACT

In a network of mobile agents, data integrity can be improved by providing an agent server that can migrate between devices operating in the region of interest (ROI). The agent server distributes agent clients onto devices in the ROI and provides agent server services to the agent clients, including receiving and storing data from the agents. When the agent server device is to leave the ROI, the agent server can migrate to any device executing an agent client and continue to provide the agent server services, including data collection and aggregation, from the device to which the agent server has migrated.

RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 15/903,684, filed Feb. 23, 2018, now pending, whichis a continuation of and claims priority to U.S. patent application Ser.No. 15/187,596, filed Jun. 20, 2016, now U.S. Pat. No. 9,948,712, whichis a continuation of and claims priority to U.S. patent application Ser.No. 12/629,945, filed Dec. 3, 2009, now U.S. Pat. No. 9,372,728, eachdisclosure of which is incorporated by reference herein in its entirety.

FIELD OF THE INVENTION

This disclosure relates to mobile agent networks and more particularlyto managing data within the network.

BACKGROUND OF THE INVENTION

Agents running on mobile devices within a region of interest (ROI) canmove or copy themselves to other devices that enter the ROI. Typically,each mobile device acts on its own without any central authority or rolein the ROI. Content acquired between various agents can be fragmentedand/or duplicated as agents move from mobile to mobile within the ROI.

What is required is a system and method that can establish a distributedclient/server relationship between various Agents that persist within aROI in order to manage the integrity of the data collected over time byagent activity.

SUMMARY OF THE INVENTION

In one aspect of the disclosure, there is provided a method for managingdata integrity of one or more agent clients within a region of interest.The method comprises providing an agent server on a first device in theregion of interest, storing data derived from at least one agent clientwith the agent server, and migrating the agent server and the storeddata to a second device in the region of interest prior to the firstdevice leaving the region of interest.

In one aspect of the disclosure, there is provided an agent serverconfigured to provide at least one agent server service from a firstdevice to at least one agent client on a second device in a region ofinterest, migrate from the first device to a third device, and providethe at least one agent server service from the third device to the atleast one agent client on the second device.

In one aspect of the disclosure, there is provided a computer-readablemedium comprising computer executable instructions for execution by afirst processor of a first device, that, when executed, cause the firstprocessor to receive an agent client from a second processor executingan agent server, execute the agent client, receive an instance of theagent server from the second processor, and execute the agent serverinstance.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made, by way of example only, to specificembodiments and to the accompanying drawings in which:

FIG. 1 illustrates a network of agents including an agent server;

FIG. 2 illustrates a process for managing the network of agents;

FIG. 3 illustrates a message flow for distributing an agent client;

FIG. 4 illustrates a process flow for distributing an agent client;

FIG. 5 illustrates a message flow for migrating an agent server;

FIG. 6 illustrates a process flow for migrating an agent server;

FIG. 7 illustrates an interaction between processes of an agent clientdevice and an agent server device; and

FIG. 8 illustrates an instruction set executable on the agent clientdevice.

DETAILED DESCRIPTION OF THE INVENTION

Early incarnations of agent applications draw from conventionalclient/server models. Modern agent-based solutions are typicallyarchitected in a different manner from traditional client/serversolutions found on traditional web-based application models. An agentrequires the use of other capable devices that are willing toparticipate within the ROI in order to persist itself. If all agentsautonomously collect information from their sensors and behaveindependently or in concert with other agents toward a goal while alsopotentially moving among devices in order to persist presence within theROI, the information collected can become redundant and/or fragmentedand introduce unnecessary complexity or noise in decision-makingprocesses.

A system 10 in accordance with an embodiment of the disclosure isillustrated in FIG. 1. In the system 10, there may be any number ofdevices 12, 13 on which instances of a client agent (14,17 respectively)are executed within a region of interest (ROI) 20. Typically, thedevices 12, 13 will be mobile devices, such as cellular phones, personaldigital assistants (PDA), netbooks, or laptops though in some cases, thedevices 12 may be static devices. The devices 12, 13 include a locationprovider 15 that enable the devices 12, 13 to know their position. Thelocation provider 15 may be capable of determining the device's locationthrough any suitable means such as through GPS, cellular system, nearfield radio, digital/video camera, triangulation and the like.

There may be defined one agent that persists a centralized role and/oracts as a centralized server, termed an agent server 16 herein. Theagent server 16 executes on a mobile device 18, which may be any devicesimilar to the devices 12, 13. The agent server 16 can be configured toprovide lifecycle management within the ROI 20 and also actively manageincoming requests from Agent Client/Proxy instances. The agent server 16implements server-side behaviors and accepts requests for thosebehaviors from Agent Client/Proxy instances. For their part, the agentclient/proxies 13, 17 may act as a simple proxy to the Agent Server 16and/or can provide a programmatic interface to other applicationsexecuting on the client device (a service). The agents 14 use access tothe client device's hardware and the Agent Server's ROI to accept/rejectrequests from other applications on the client device.

The agents 14 may communicate with the agent server through any suitableprotocols and processes known to a person skilled in the art, such as(SOAP, XML, HTTP, HTTPS, etc) and it is not considered that furtherdefinition or description of these protocols and processes is requiredherein. Typically, an agent client 14,17 will continually seek an agentserver, such as by repeatedly submitting an agent participation requestas will be described below, until it receives a response from an agentserver. The agent server response may tell the client it has entered theboundaries of a ROI.

A process for managing the network of agents is shown in the flowchart100 of FIG. 2. At step 101, an agent server is provided on a firstdevice in the region of interest. Data derived from at least one agentclient within the region of interest is received and stored with theagent server (step 102). When required, such as prior to the agentserver device leaving the ROI, the agent server is migrated to a seconddevice together with the stored data (step 103). Data stored by theagent server may be data directly received from agent clients or may bedata that is derived through analysis and interpretation of agent clientdata.

The agent server initially provides agent server services to agentclients within the network from the first device. After migration, theagent server 16 is able to continue providing the agent services fromthe device to which it has migrated. The services provided by the agentserver 16 to the agent clients 14, 17 will depend on the application andimplementation of the agent client network. Examples of agent serverservices may include, without limitation, traffic congestion and trafficemergency management, fire emergency management and rescue management aswell as many other location dependent or ROI dependent services.

As mentioned above, a function of the agent server 16 is to distributeclient agents 14 across participant devices 12. Message flow for thistask is illustrated in FIG. 3 and the corresponding process is shown inthe flowchart 200 of FIG. 4. At commencement, it is assumed that theagent server 16 is running on Device1 18 and that an agent clientbootstrap code 33 is running on Device2 12. The bootstrap code 33includes a loop in which Device2 12 broadcasts an agent clientparticipation request 41 from the device 12 (step 201) and awaits anagent client activation request in response (step 203). If no agentclient activation request is received, then a timeout occurs (step 205),a failure is recorded 207 and the bootstrap code returns to step 201.Device2 may broadcast the participation request irrespective of whetherit is in the ROI or not. The agent client participation request 41specifies an ID of the device 12 and a location, as determined by thedevice's location provider.

The agent server 16 on Device1 18 also executes a loop in which theagent server 16 waits for agent client participation requests 202 untila timeout occurs 204. When Device2 enters the ROI, the participationrequest 41 is detected by the agent server 16 on Device1 18 (step 206)so that no timeout occurs at step 204. The agent server 16 processes thebroadcast participation request 41 and determines if Device2 is withinthe ROI (step 208). If Device2 is not within the ROT, then the agentserver 16 ignores the participation request and returns to step 202. IfDevice2 is within the ROI, then the agent server 16 responds with anagent client activation request (step 210) indicating the agent clientID and ROI and including a serialized instance of the agent client. Theagent server 16 then waits for an agent client activation response 212and records a failure 216 if a timeout occurs 214.

If the agent client activation request 42 is received into Device2before the timeout at step 205, then the bootstrap code 33 processes theagent client activation request (step 209) including deserializing andactivating the agent client 14 (step 211). If the agent client cannot besuccessfully activated, then a failure is recorded 207 and the clientbootstrap returns to step 201, thereby causing the timeout 214 in theagent server 16. If the agent client 14 is successfully activated inDevice2 12 (step 213), then the agent client 14 generates and sends anagent client activation response 43 to the agent server 16 (step 215).The agent client activation response 43 indicates the agent client ID,the device ID of Device2 12 and a success or failure indicator. If theagent client activation response 43 is received in the agent server 16before the timeout 214, then the agent server records the new agentclient for the server 218, including recording a reference thatassociates the device ID with the agent client ID. The Agent Server usesthe reference for future communication with other activated agents inthe ROI.

Once the Agent Server has distributed the Agent Client, the Agent Serverand Agent Client form part of a framework for any number ofapplication-specific features. The standard operating interactionbetween the agent server and the agent client will thus depend on theapplication (or the goal of the Agent) in the region. The Agent Serverdefines the boundary and existence of the ROI and provides a dataaggregator for all Agent Clients in the ROI. Thus, when an agent clientleaves the ROI, the data accumulated by the agent client is retained inthe agent server which collectively manages all the fragments ofinformation from the various agent clients.

There will be times when it is necessary for the agent server 16 tomigrate from its device 18 to another device 12 in order for the agentserver 16 to persist within the ROI 20. Examples of when an agent servermay need to migrate include an impending near-term hardware failure(power supply failure, decreased bandwidth, etc) or as a result in theuser's change of command (e.g. when a fire chief enters the ROI for anemergency and needs to take charge). For example, with reference to FIG.1, the agent server 16 may be executing on Device1 18 with instances ofthe agent client 13,17 executing on Device2 12 and Device3 13respectively, all of which reside in the ROI 20. FIG. 5 illustrates themessage flow of one embodiment when the agent server 16 migrates toanother device. A migration process is shown in the flowchart 300 ofFIG. 6. At step 302, it is determined that the agent server 16 is tomove from Device1 18. Candidate devices include any device currentlyhosting an agent client, since such devices all reside in the ROI, and asuitable device (e.g. Device2 13) is chosen at step 304. At step 306,the agent server 16 sends an agent server participation request 51 tothe agent client 14 on Device2 12. The agent server participationrequest includes the device ID of Device2 12 and the agent ID currentlyrunning on Device2. The agent server 16 waits for a response at step 308while the agent client 14 receives the agent server participationrequest 51 at step 301 and determines if the device hosting the agentclient 14, i.e. Device2 12 is capable of hosting the agent server 16(step 303). The agent client 14 sends an agent server participationresponse 52 indicating if Device2 can host the agent server (step 305)or not (step 307). The agent server participation response identifiesthe DeviceID of Device2 12, the agent ID of agent client 14 and a valueindicating whether the agent client can receive the agent server.Possible values for this value may include YES, NO or NEVER.

If the agent client 14 indicates in the agent server participationresponse 52 that Device2 12 is capable of hosting the agent server 16,then the agent client 14 proceeds to wait for activity from the agentserver 16 (step 309). If the agent server participation response 52received by the agent server 16 indicates that the agent client 14 isunable to host the agent server (step 310), then a failure is recorded312 and the agent server process returns to step 304 to search for anext possible candidate host. If the agent server participation responseis deemed successful 310, then agent server 16 begins preparations tomigrate, including rejecting new service requests and resolvingoutstanding requests 314. The agent server 16 then sends an agent serveractivation request 53 to the agent client (step 316), which includes aDeviceID of Device2, a serialized agent server and stored content of theagent server such as agent and device identities of other agents in theROI, aggregated data collected from other agents, the ROI definition,etc. The agent server 16 then continues to reject further servicerequests while waiting for an activation response from the agent client14 (step 318).

The agent client 14 processes the agent client activation request 53(step 311) by deserializing and activating the agent server 50 onDevice2 12 (step 313). An agent server activation response 54 is sentindicating whether the agent server was successfully activated (step317) or not (step 319). If the agent server 16 receives a successfulindication (step 320), then the agent server 16 is terminated on Device116 (step 322) or placed on standby. Otherwise, the agent server 16resumes agent server processing 324 and returns to step 304 to seekanother potential candidate device for hosting the agent server.

Once the agent server 50 is successfully activated on the new device,i.e. Device2 12, then the agent client 14 currently running on thedevice is terminated 321 and agent server reset messages 55 are sent toother agent clients on the network, such as agent client 17 running onDevice3 13. The agent server reset messages indicate the old device IDand the new device ID, i.e. Device1 and Device2 respectively, as well asthe agent ID of the new agent server 50. The agent server reset messagethus causes the agent client 17 on Device3 13 to reference the new agentserver 50 on Device2 12. Device3 can then continue receiving agentserver services from the agent server, albeit from the new device(Device2).

Because the agent server can migrate with its collected data betweendevices, the agent server's movement does not necessarily have to impactthe integrity of the agent data collected over time by other agents alsowithin the ROI. Furthermore, since the agent clients communicate data toonly a single agent server, redundant information between Agents withina ROI can be reduced or eliminated and the agent server can preserveinformation exclusive to one Agent within the ROI as the Agent leavesthe ROI.

The components of the system 10 may be embodied in hardware, software,firmware or a combination of hardware, software and/or firmware. In ahardware embodiment, Device2 12 may include a processor 61 operativelyassociated with a memory 62 as shown in FIG. 7. The memory 62 may storean instruction set 400 executable by the processor 61 which may includethe bootstrap code described above. When executed, the instruction set400, shown in FIG. 8, causes the processor to receive an agent clientfrom a processor 71 that is executing an agent server, such as aprocessor of Device1 18. The processor 61 may receive the agent clientinstance (step 401) from the processor 71 through any suitablecommunications link 65 of the network. Once received, the processor 61executes the agent client (step 402). At some later time when the agentserver migrates, the processor 61 may receive an instance of the agentserver from the Device1 processor 71 (step 403) and execute the agentserver instance (step 404). Receiving and executing the agent serverinstance may cause the Device2 processor 61 to terminate the agentclient on the processor 61. The Device2 processor 61 may also notify athird processor (not shown) such as a processor of Device3 13 to causethe third processor to associate the agent server with Device2 so thatDevice2 is able to provide agent server services to an agent client onDevice3.

Although embodiments of the present invention have been illustrated inthe accompanied drawings and described in the foregoing description, itwill be understood that the invention is not limited to the embodimentsdisclosed, but is capable of numerous rearrangements, modifications, andsubstitutions without departing from the spirit of the invention as setforth and defined by the following claims. For example, the capabilitiesof the invention can be performed fully and/or partially by one or moreof the blocks, modules, processors or memories. Also, these capabilitiesmay be performed in the current manner or in a distributed manner andon, or via, any device able to provide and/or receive information.Further, although depicted in a particular manner, various modules orblocks may be repositioned without departing from the scope of thecurrent invention. Still further, although depicted in a particularmanner, a greater or lesser number of modules and connections can beutilized with the present invention in order to accomplish the presentinvention, to provide additional known features to the presentinvention, and/or to make the present invention more efficient. Also,the information sent between various modules can be sent between themodules via at least one of a data network, the Internet, an InternetProtocol network, a wireless source, and a wired source and viaplurality of protocols.

What is claimed is:
 1. An agent server device configured to collectmeasurements from different geographic locations within a Region OfInterest (ROI) by providing lifecycle management for aremotely-operational client agent including local retention of dataaccumulated by the client agent, the agent server device comprising: amemory device configured to store instructions; and a processing deviceconfigured to execute the instructions stored in the memory device to:identify candidate remote mobile devices near a boundary of the ROI;distribute an instance of the client agent to a remote mobile device ofthe candidate remote mobile devices following an ingress of the remotemobile device into the ROI to utilize one or more sensors of the remotemobile device to collect at least one of the measurements; and followingdistribution of the instance of the client agent to the remote mobiledevice, request migration of data collected by the instance of theclient agent from the remote mobile device to the agent server deviceprior to any egress of the remote mobile device from the ROI.
 2. Theagent server device of claim 1, wherein identifying candidate remotemobile devices near the boundary of the ROI comprises identifyingparticipation requests repeatedly broadcast from each of the candidateremote mobile devices irrespective of whether said candidate remotemobile device is within the ROI or not.
 3. The agent server device ofclaim 2, wherein the processing device is further configured to notifythe remote mobile device about the ingress by transmission of an agentclient activation request to the remote mobile device in response to acorresponding one of the participation requests.
 4. The agent serverdevice of claim 3, wherein the processing device is further configuredto record a reference corresponding to the remote mobile device inresponse to receipt of an activation response to the agent clientactivation request, the activation response from the instance of theclient agent distributed to the remote mobile device.
 5. The agentserver device of claim 3, wherein the agent client activation requestincludes the instance of the agent client.
 6. The agent server device ofclaim 2, wherein the processing device is further configured to record areference that associates a device identifier of the remote mobiledevice with an identifier present in the corresponding one of theparticipation requests.
 7. The agent server device of claim 2, whereinthe processing device is further configured to ignore participationrequests that correspond to at least one candidate mobile device outsidethe boundary.
 8. The agent server device of claim 1, wherein the datacomprises first data, and wherein the processing device is furtherconfigured to derive second data from the first data.
 9. The agentserver device of claim 1, wherein the instance of the client agentcomprises a serialized instance of the client agent.
 10. The agentserver device of claim 1, wherein the agent server device comprises amobile device.
 11. The agent server device of claim 1, wherein the agentserver device comprises a static device.
 12. A method of collectingmeasurements from different geographic locations within a Region OfInterest (ROI) by providing a management device for aremotely-operational client agent including local retention of dataaccumulated by the client agent, the method including: identifying, bythe management device, candidate remote mobile devices near a boundaryof the ROI; distributing, by the management device, an instance of theclient agent to a remote mobile device of the candidate remote mobiledevices following an ingress of the remote mobile device into the ROI toutilize one or more sensors of the remote mobile device to collect atleast one of the measurements; and following distribution of theinstance of the client agent to the remote mobile device, migrating datacollected by the instance of the client agent from the remote mobiledevice to the agent server device prior to any egress of the remotemobile device from the ROI.
 13. The method of claim 12, whereinidentifying, by the management device, the candidate remote mobiledevices near the boundary of the ROI further comprises: identifying, bythe management device participation requests repeatedly broadcast fromeach of the candidate remote mobile devices irrespective of whether saidcandidate remote mobile device is within the ROI or not; and notifyingthe remote mobile device about the ingress by transmission of an agentclient activation request from the management device to the remotemobile device in response to a corresponding one of the participationrequests.
 14. The method of claim 13, further comprising recording onthe management device a reference corresponding to the remote mobiledevice in response to receipt of an activation response to the agentclient activation request, the activation response from the instance ofthe agent client distributed to the remote mobile device.
 15. The methodof claim 13, wherein the agent client activation request includes theinstance of the agent client.
 16. The method of claim 13, furthercomprising recording on the management device a reference thatassociates a device identifier of the remote mobile device with anidentifier present in the corresponding one of the participationrequests.
 17. The method of claim 12, wherein the data comprises firstdata, and wherein the method further comprises deriving, by themanagement device, second data from the first data.
 18. The method ofclaim 12, wherein the management device comprises a mobile device. 19.The method of claim 18, wherein a first hardware of the mobile device isequivalent with a second hardware of the remote mobile device.
 20. Themethod of claim 18, wherein the management device comprises a staticdevice.